Repository navigation
[UPDATE][vaultwarden][1.0.4] Upgrade Vaultwarden 1.36.0 to 1.37.5 - #3913
Merged
Terminus-Gitbot merged 1 commit intoNov 7, 2026
Merged
Conversation
- chart version 1.0.3 -> 1.0.4; appVersion / versionName / image.version -> 1.37.5 - image tag is hardcoded in templates/vaultwarden.yaml:22 (values.yaml image.version is not referenced by the template), so both places are bumped to stay in sync - verified docker.io/vaultwarden/server:1.37.5 exists in the registry tag list - 1.37.0 through 1.37.5 are all security releases: 8 Medium advisories in 1.37.0, one High (organization member revocation GHSA-69q9-v8p6-xvx3) plus five Medium in 1.37.4, and two Medium in 1.37.5 - add upgradeDescription (root + en-US + zh-CN); call out that 1.37.5 validates configuration strictly and invalid values now abort startup, and that 1.37.0 rejects an unrecognised DATABASE_URL instead of falling back to SQLite - no config or env var change in this chart; /data volume is reused as-is
Collaborator
|
Check passed, please wait for auto-merge. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upgrade Vaultwarden from
1.36.0to1.37.5in the Olares appvaultwarden, chart version1.0.3->1.0.4.This is a security-driven upgrade: every release from
1.37.0to1.37.5is a security release.Changes (6 files, +27 −6)
Chart.yamlversion: 1.0.3 -> 1.0.4,appVersion: 1.36.0 -> 1.37.5OlaresManifest.yamlmetadata.version -> 1.0.4,spec.versionName -> 1.37.5, addupgradeDescriptioni18n/en-US/OlaresManifest.yamlupgradeDescriptioni18n/zh-CN/OlaresManifest.yamlupgradeDescriptionvalues.yamlimage.version: 1.36.0 -> 1.37.5templates/vaultwarden.yaml:1.36.0 -> :1.37.5As with
fastnotesync, this chart does not reference.Values.image.versionin its templates — the tag is hardcoded attemplates/vaultwarden.yaml:22, so both places had to change. No template logic or values structure was modified.Security content of this upgrade
Upgrade notes surfaced to users
LOGIN_RATELIMIT_MAX_BURST,TRASH_AUTO_DELETE_DAYS,EVENTS_DAYS_RETAIN,SMTP_TIMEOUTabove 65535;EMAIL_ATTEMPTS_LIMITabove 255), rate-limit or DB timeouts below 1,DATABASE_MIN_CONNS > DATABASE_MAX_CONNS, or an invalid cron inDUO_CONTEXT_PURGE_SCHEDULE/PURGE_INCOMPLETE_SSO_AUTHwill stop the container.DATABASE_URLinstead of silently falling back to SQLite.v2026.10.1; required for web vault 2026.7.1+ two-step login toggling and 2026.9.0+ emergency-access takeover.SIGNUPS_ALLOWED,WEBSOCKET_ENABLED,ADMIN_TOKEN; no new variable,/datavolume reused.Verification
docker.io/vaultwarden/server:1.37.5exists — confirmed against the registry tag list (309 tags,1.37.xseries ends at1.37.5).Chart.yaml:version=metadata.version=1.0.4;Chart.yaml:appVersion=spec.versionName= image tag =1.37.5.upgradeDescriptionidentical between root manifest andi18n/en-US; zh-CN mirrors it line by line.git diff --checkclean; diff limited to the 6 files above.upstream/main(f012d1c0), no merge commit.